home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
vwansi20.zip
/
VWANSI.DOC
< prev
next >
Wrap
Text File
|
1991-12-14
|
12KB
|
293 lines
Online ANSI Viewer v. 2.0
(c) 1991 E.L. Morrow
written in Turbo Pascal 5.5
utilizing RMDOOR 1.0
-by-
E.L. Morrow
Work of Art BBS (SysOp) (707)465-3193
Voice Phone (707)465-6765 9:00am-9:00pm
BBS Node 2 9:00pm-9:00am
(For Validated Members only!)
DISCLAIMER:
I relinquish any and all responsibility for anything that may
occur due to the use of this program, correctly or incorrectly. I am
in no way libel for any damage that is attributed to the use of this
program by any and all persons.
SHAREWARE:
Online ANSI Viewer v2.0 is ShareWare. It's not crippled or
anything, but it does let your users know that it isn't registered by
showing #UNREGISTERED# at the top of the header on the selection menus.
Registration is only $15 for this new version. Future upgrades
will be priced accordingly depending on how much is changed and added.
Anyone who registers now will never have to pay for another registration
of this program. Your registration number will be good for all versions.
Distribution of this program will be solely the province of the
large number of BBS's across the country. I can't afford to send disks
out to people who register. I know this sounds kind of crude, but if
you enclose your BBS number when you register along with a password to
get on your system, I'll upload the latest version (if it's different)
and send you a private message in an appropriate conference that will
list your registration information (just a reg number and name actually).
Print and fill out the form in this archive called TTANSI.REG
and mail it to:
Elm L. Morrow
911 N. Pacific Ave Apt 15
Crescent City, CA 95531
Make checks or money orders payable to: Elm L. Morrow
SETTING UP:
This new version of the ANSI Viewer is multi-node. In order to
use this door on a multi-node BBS you need to have a configuration file
for each node. All of the files in the archive and the configurations
should be put into their own directory.
Setting up the Viewer is fairly easy. The first thing you need
to do is set up the config files. They don't *have* to be called
VWANSI1.CFG, VWANSI2.CFG, etc... , but it maintains clarity and ease
of use if they are. They take this form:
PCB {BBS Type}
C:\BBS {Dir of the node's door files}
Works of Art BBS {Name of BBS--registration name}
Elm Morrow {Sysop's full name}
0 {locked baud rate}
NOT REGISTERED {registration number}
BBS Type can be of several types:
PCB PCBoard
GAP GAP (DOOR.SYS)
SF Spitfire,
RBBS RBBS
WC WildCat!
Wildcat 3.XX uses GAP (DOOR.SYS) the VWANSI.CFG would appear as
follows:
GAP
c:\WC30\DOORS\(subdir name)
your BBS name
sysop name
0
NOT REGISTERED
Location of definition files is the directory where your door
files are when the BBS shells out to the door. In other words, if
you're running PCBoard, line 2 needs to point to the location of
PCBOARD.SYS, PCBOARD.DAT, and USERS for that node.
BBS Name or registration name goes on line 3 of the config file.
I guess if you can't work that one out, I can't help you much! <grin>!
SysOp Name should be the main SysOp's name as it appears in the
BBS configuration. It's not really critical.
Locked baud rate is for high speed modems. If you lock your port
at 19200 or 38400, put it here in that form (i.e. 19200 or 38400). This
door does not require a FOSSIL driver to run at high speeds. If you
have trouble, please contact me! There have been some reports of
problems with CompuComs but the USR Dual Standards aren't having any
trouble. I myself own a CompuCom Champ and the problem only seems
to occur with a Champ to Champ connection. <sigh>....
Registration number is the number you get from me that will replace
the word #UNREGISTERED# in the header of all the menus to whatever your
BBS name is (or whatever you register under---best to choose the BBS name).
Okay! Now for the stuff that isn't quite so easy.... In addition
to the configuration file, you need some definition files for the list
of categories and a list of files for each category. I know, I know, who
needs manual setup? Well, register the darn door and I'll put together
an automated/assisted setup program!
Here are the files and their formats:
CATEGORY.DAT
------------
This file contains the list of categories to display on the initial
category menu. It's very simple. It's just a text file that contains
*SINGLE LINE ENTRIES* that define each element on the menu. The format
goes a little something like this:
<category file>,<category description>,<security level>
The first part, <category file>, is the name (and path if it's in
a separate directory) of the file that contains the list of files in
this category. See below.
<category description> is what the user will see when they are
making their selections from the category menu. It can be up to 50
characters in length.
<security level> is the minimum security level the user must have
in order to be able to view this category. Just set it to 0 if you don't
really care. This is for those SysOps out there that like to segment
everything they do into different levels of access.
*MAKE SURE YOU SEPARATE EACH FIELD WITH COMMAS!!!*
Category files
--------------
Category files can have any name and/or extension that you want
to give them. I prefer to use the extension .CAT so I know what the
file is for. It is also a normal text file that contains a list of
single line entries. These entries will tell the computer what files
to display and where they are. The form is similar to the CATEGORY.DAT
file:
<d:\path\name.ext>,<file description>,<security level>
The first element *must* be the full path and name of the file
that the user will view when they choose each selection. If the file
resides in the same directory as VWANSI, then you only need to provide the
name and the extension.
<file description> is what the user will see when they are making
their choices from the ANSI Files menu (or whatever the heck I called it).
It can be up to 50 characters in length.
<security level> is the minimum security the user must have in
order to view the individual file. A little redundant, but it's very
easy to put a ,0 at the end of each line. But, it's impossible to not
show the selection without this field if you want only some people to
be able to see it. This will help avoid creating multiple categories
for different levels.
That's it! (as if that weren't enough! <grin>) It may seem like
a lot to do, but if you don't have to put a bunch of categories and lists
together all at once, it's easy to maintain and all of this can be done
remotely by co-SysOps and other lesser BBS personalities <grin> (don't
get upset! *I* used to be a co-SysOp that got to do the grunt work
while *their* name went up in lights!)
RUNNING THE DOOR:
The batch file for this door is simple. Do something like this:
cd c:\bbs\doors\vwansi
vwansi vwansi1.cfg
cd c:\bbs
board
There are many BBS schemes for setting up doors, so if this batch
file doesn't work for you, just read your doc's and find out how to run
doors.
SPECIAL SYSOP KEYS:
Key(s) Function
------ ---------
Scroll If the Scroll Lock key is ON, you will here music
Lock locally. If it's off, you will not.
HOME Toggles between the user status window and a
help display that lists the RMDoor special
keys.
F6 Takes 5 minutes away from the caller.
F7 Gives 5 minutes to the caller.
F9 Quit the door and return the caller to the
BBS.
F10 Enter chat mode. Pressing the ESC key exits
the chat mode.
Alt+D Drop to DOS.
USING THE DOOR:
This is the easiest part. All the user has to do is enter the
door and make menu selections! *You've* done all the work! Here are
the few keys they need to know (they're informed while they're in the
door by a footer listing currently acceptable inputs.)
<2> - Go down one selection
<8> - Go up one selection
<ENTER>- Choose current selection
<ESC> - Exit to last menu or the BBS
That's it!
It came to mind a little too late for this release, but the menus
support multiple pages. If there are more selection beyond the end of
the ones currently viewed (11 at a time), pressing <2> one more time will
display the next set of selections. Likewise, pressing <8> at the top of
the menu box will bring the previous page up. I'll make a note of that
and put it on the display for the next upgrade (definitely will be one).
SUGGESTIONS, ETC...:
I want to extend my gratitude to Randy Hunt for making this door
possible. He gave me a lot of help getting it to work with file sharing
and he deserves a lot of credit. (Take a bow, Randy).
Please leave your suggestions for improvements and any other
comments on one or more of the following boards:
The Works of Art BBS (This is my board)
(707) 465-3193 (Node 1) or
(707) 465-6765 (Node 2) from 9:00pm to
9:00am.
Conference: Mail Room
The WheelChair Express
(707) 464-3705 Node 1
(707) 465-1272 Node 2
Conference: Message Center
Of course, there's always snail mail. As a general rule, I don't
like answering letters, but if you send a check or m.o. for $15 with a
letter, I'll more than likely get in touch with you one way or the other.
If I've missed something or you can't make sense out of all or part
of this .DOC file, get in touch and let me know. It's really not that
hard to get it set up, but I don't always feel like writing and so the
descriptions of how to do things get erratic and confusing. <Sigh>
KNOWN BUGS:
For some reason when one of my ßeta tester who uses a CompuCom
Champ hooks up with another CompuCom, it blows the display. It doesn't
lock up the board or anything, but it just won't show the displays
correctly. We're currently trying to get that worked out.
HISTORY:
Version 1.1
was released simply to remove the ShareWare notice that
my door unit was putting just before entry to the door. I'm registered
now, so it's gone.
Version 2.0
This new multinode version now supports ANSI music!
Added a local music on/off toggle (scroll lock) and
cleaned up the music routines a little.